Skip to content

Uses GitHub Actions for tests and releases. #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Uses GitHub Actions for tests and releases. #61

wants to merge 6 commits into from

Conversation

@fdcastel
Copy link
Member

@fdcastel fdcastel commented Nov 18, 2025 •
edited
Loading

Fix #60.

ToDo:

  • Update tests to use remote Firebird servers
  • Use Docker for Firebird server
  • Run tests on Linux
  • Build and publish to GitHub Releases
  • Publish to GitHub Packages (unsupported)
  • Publish to PyPI (test on official repository)
  • Run tests on Windows
  • Set Python package version from Git Tag.

Remarks:

  • Tests no longer require a local Firebird server.
    • They now run in the CI workflow using official Firebird Docker images.
    • Please review the associated test changes and the FIXME: comments.
  • Unofficial builds are available at: https://github.com/fdcastel/python3-driver/releases
    • I just found a minor glitch: package version is hardcoded as 2.0.2. It should be set from Git Tag.
    • Fixed using hatch-vcs
  • The workflow should now publish to PyPI upon correct configuration.
    • I couldn't verify this due to current GitHub Packages currently not supporting Python packages.

@fdcastel fdcastel changed the title Fix issue 60 Uses GitHub Actions for tests and releases. Nov 18, 2025
@fdcastel
Copy link
Member Author

fdcastel commented Nov 18, 2025

Fixed the version using hatch-vcs.

Summary:

  • hatch-vcs automatically detects versions from git tags (e.g., v2.0.3-beta1 → 2.0.3b1)
  • When you push a tag like v2.0.3-beta1, the workflow will build packages with the correct version
  • No manual version updates needed - just create and push git tags
  • The version is baked into the package metadata at build time
  • The __VERSION__ variable imports from the package metadata at runtime

Tag Format:

hatch-vcs follows PEP 440 conventions:

  • v2.0.3 → 2.0.3
  • v2.0.3-beta1 → 2.0.3b1
  • v2.0.3-rc1 → 2.0.3rc1
  • v2.0.3-alpha1 → 2.0.3a1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Publish from GitHub Actions?

1 participant

@fdcastel